Method for automatically switching operation profiles on a mobile device and system thereof

ABSTRACT

A method for automatically switching operation profiles on a mobile device includes storing an operation profile database having a plurality of operation profiles; mapping a velocity range to each operation profile to thereby form a velocity and profile table; monitoring a velocity of the mobile device; and switching between the operation profiles of the mobile device according to the velocity of the mobile device, and the velocity and profile table.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a method for automatically switchingoperation profiles on a mobile device and system thereof, and moreparticularly, a method for automatically switching operation profiles ona mobile device according to the velocity of the mobile device and avelocity and operation profile table, and a related mobile device.

2. Description of the Prior Art

Mobile devices such as mobile phones are becoming increasingly popularin urban society. We take them with us wherever we go: the office, home,to the beach, on airplanes, to the movies. Each of these environmentsrequires care to be taken based on proper modern etiquette as well asgovernment and safety regulations. For example, it is considered commoncourtesy to lower the ring/sound volume on your mobile/portable devicewhen in a quiet setting such as the office, and to shut it off or set it“on vibrate” when in a movie theatre. In moving vehicles, other rulesshould also be adhered to: it is forbidden by many federal andinternational regulations to operate a mobile wireless device while inan airplane, and many states in the USA have varying laws restricting orprohibiting the use of mobile phones while driving.

Most, if not all, mobile device manufacturers have addressed the varioussituations by allowing users to have multiple operating profiles(commonly called “profiles”) on the mobile phone (for example), eachprofile having different settings: ring volume, selected ring tone,vibrate on/off, keypad tones, display brightness, etc. Mobile phoneusers manually set the profile to use, according to their immediateenvironments and/or their preferences at the time. It is, however,rather easy (and common) for users to forget to switchprofiles—particularly from a louder profile to a softer one—much to thechagrin of those around him/her. In circumstances where the turning offof mobile devices is in compliance with regulations, forgetting toswitch to that profile could result in prosecution and disciplinaryaction.

As such, there is a need to provide a manner by which the user needn'tmanually switch profiles, be it for courtesy or safety reasons.

SUMMARY OF THE INVENTION

It is therefore an objective of the present invention to solve theaforementioned problems, and to provide a method for automaticallyswitching operation profiles on a mobile device, the method comprisingstoring an operation profile database having a plurality of operationprofiles, mapping a velocity range to each operation profile to therebyform a velocity and profile table, monitoring a velocity of the mobiledevice and switching between the operation profiles of the mobile deviceaccording to the velocity of the mobile device, and the velocity andprofile table. Such a method alleviates the user from manually switchingoperating profiles, avoiding unnecessary (and often unintentional)discourtesy and/or law-breaking, as well as mitigating safety risks.

These and other problems are generally solved or circumvented, andtechnical advantages are generally achieved, by advantageous embodimentsof the present invention, which includes a method as above, furthercomprising storing a current operation profile as a previous operationprofile of the mobile device when switching to a new operation profile,and returning to the previous operation profile when the velocity of themobile device is within the velocity range of the previous operationprofile.

In another embodiment, a method further comprises notifying a user whenswitching between operation profiles of the mobile device. Oneembodiment further comprises switching between the operation profiles ofthe mobile device further according to a user confirmation, whereinswitching between the operation profiles of the mobile device can berejected by the user.

An embodiment further comprises switching between the operation profilesof the mobile device further according to the historical userpreferences. Another comprises switching to a target operation profilewhen the velocity of the mobile device is within the velocity range ofthe target operation profile.

An extension of the above embodiments further comprises mapping anentering velocity range and an exiting velocity range to each operationprofile in the velocity and profile table, and switching to a targetoperation profile when the velocity of the mobile device is within theentering velocity range of the target operation profile and is outsideof the exiting velocity range of a current operation profile, whereinthe entering velocity range is different from the exiting velocityrange.

Another method according to the present invention further comprisesranking a priority order of the operation profiles, determining at leastone candidate operation profile for which the velocity of the mobiledevice is within the velocity range of the candidate operation profile,and switching to a target operation profile being a candidate operationprofile having a highest priority. As an option, the priority order canbe determined in order of descending velocity range.

The present invention, in one embodiment, is a mobile device forautomatically switching operation profiles, comprising an operationprofile database having a plurality of operation profiles, a velocityand profile table formed by mapping a velocity range to each operationprofile, a velocity monitoring module for monitoring a velocity of themobile device, and an operation profile switching module for switchingbetween the operation profiles of the mobile device according to thevelocity of the mobile device, and the velocity and profile table.

In one embodiment, the operation profile switching module from above isfurther for storing a current operation profile as a previous operationprofile of the mobile device when switching to a new operation profile,and for returning to the previous operation profile when the velocity ofthe mobile device is within the velocity range of the previous operationprofile. In another embodiment, the operation profile switching moduleof the mobile device is further for switching to a target operationprofile when the velocity of the mobile device is within the velocityrange of the target operation profile. Alternatively, the velocity andprofile table is further for mapping an entering velocity range and anexiting velocity range to each operation profile in the velocity andprofile table, and the operation profile switching module is further forswitching to a target operation profile when the velocity of the mobiledevice is within the entering velocity range of the target operationprofile and is outside of the exiting velocity range of a currentoperation profile, and the entering velocity range is different from theexiting velocity range.

A mobile device of the present invention, like the related methods, canfurther provide for ranking a priority order of the operation profiles,determining at least one candidate operation profile for which thevelocity of the mobile device is within the velocity range of thecandidate operation profile, and switching to a target operation profilebeing a candidate operation profile having a highest priority. Thispriority order could be determined in order of descending velocityrange.

The velocity monitoring module of the mobile device can utilize a GlobalNavigation Satellite System (GNSS) device, such as a Global PositioningSystem (GPS) device.

The foregoing has outlined rather broadly the features and technicaladvantages of the present invention in order that the detaileddescription of the invention that follows may be better understood.

Additional features and descriptions of the present invention will bedescribed hereinafter which form the subject of the claims of thepresent invention. It should be appreciated by those skilled in the artthat the conception and specific embodiments disclosed may be readilyutilized as a basis for modifying or designing other structures orprocesses for carrying out the same purposes of the present invention.It should also be realized by those skilled in the art that suchequivalent constructions do not depart from the spirit and scope of theinvention as set forth in the appended claims.

These and other objectives of the present invention will no doubt becomeobvious to those of ordinary skill in the art after reading thefollowing detailed description of the preferred embodiment that isillustrated in the various figures and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention, and theadvantages thereof, reference is now made to the following descriptionstaken in conjunction with the accompanying drawings, in which:

FIG. 1 shows a flowchart for automatically switching operation profileson a mobile device according to an embodiment of the present invention.

FIG. 2 is a diagram of example velocity ranges and operation profiles.

FIG. 3 is a state diagram for an embodiment of the present invention.

FIG. 4 shows a method according to an embodiment of the presentinvention, suggesting an interaction between a mobile device and ageographic information system (GIS) module or device.

FIG. 5 illustrates a method according to another embodiment of thepresent invention.

FIG. 6 is a method for monitoring the velocity of the mobile device,according to another embodiment of the present invention.

FIG. 7 shows an exemplary priority ranking according to one embodimentof the present invention.

FIG. 8 is a block diagram of a mobile device according to one embodimentof the present invention.

Corresponding numerals and symbols in the different figures generallyrefer to corresponding parts unless otherwise indicated. The figures aredrawn to clearly illustrate the relevant aspects of the preferredembodiments and are not necessarily drawn to scale.

DETAILED DESCRIPTION

Certain terms are used throughout the following description and claimsto refer to particular system components. As one skilled in the art willappreciate, manufacturers may refer to a component by different names.This document does not intend to distinguish between components thatdiffer in name but not function. In the following discussion and in theclaims, the terms “including” and “comprising” are used in an open-endedfashion, and thus should be interpreted to mean “including, but notlimited to . . . .” The terms “couple” and “couples” are intended tomean either an indirect or a direct electrical connection. Thus, if afirst device couples to a second device, that connection may be througha direct electrical connection, or through an indirect electricalconnection via other devices and connections.

As mentioned, there is a need to provide a method for automaticallyswitching operation profiles on a mobile device. FIG. 1 shows aflowchart 100 for automatically switching operation profiles on a mobiledevice according to an embodiment of the present invention. Providedthat substantially the same result is achieved, the steps of the processflowchart need not be in the exact order shown and need not becontiguous; that is, other steps can be intermediate. The embodiment ofthe method according to the present invention includes the followingsteps:

-   Step 110: Store an operation profile database.-   Step 130: Map a velocity range to each operation profile into a    velocity and profile table.-   Step 150: Monitor the velocity of the mobile device.-   Step 190: Switch between the operation profiles of the mobile device    according to the velocity of the mobile device.

As shown in FIG. 1, the flowchart 100 begins with Step 110 storing anoperation profile database having a plurality of operation profiles.These operation profiles can be similar to what is currently found inmobile phones: a “meeting” profile, an “airplane” mode, etc. After anumber of profiles has been defined and stored, Step 130 proceeds withmapping a velocity range to each operation profile to form a velocityand profile table. From the velocity and profile table, one can map froma velocity range to a corresponding profile and/or vice versa. After theoperation profile database and the velocity and profile table have beenconfigured, Step 150 monitors the velocity of the mobile device; thiscan be done on a continuous basis or sporadically (e.g., once every Xseconds or Y minutes, based on design requirements). For Step 150,although monitoring the velocity could be achieved through the use of anaccelerometer or similar sensor, a preferred implementation of thismethod would utilize a Global Navigation Satellite System (GNSS) device,including popular Global Positioning System (GPS) technologies.

According to the velocity of the mobile device and the velocity andprofile table, the method switches between the operation profiles of themobile device (Step 190). More specifically, a preferred clarificationfor Step 190 is where the method switches to a target operation profilewhen the velocity of the mobile device is within the velocity range ofthat target operation profile. For instance, when an operation profilecalled “Car” has been defined, and a velocity range of between 10 kmphand 150 kmph has been mapped to the “Car” profile, Step 190 switches themobile device's operation profile to “Car” when the velocity of themobile device is determined to be within the 10-150 kmph range.

An extension of the above method, the method can further map an enteringvelocity range and an exiting velocity range to each operation profilein the velocity and profile table, where the entering and exitingvelocity ranges can be different. Then, the method switches to a targetoperation profile when the velocity of the mobile device is within theentering velocity range of the target operation profile and is outsideof the exiting velocity range of a current operation profile. As anexample, please refer to FIG. 2 for a diagram of example velocity rangesand operation profiles. The diagram 200 of FIG. 2 shows three differentoperation profiles—“Walk”, “Car”, and “Airplane”—each with associatedentering and exiting velocity ranges. The “Walk” operation profile hasan entering velocity range 210 comprising a lower bound 213 (at 0 kmph)and an upper bound 216 (at 5 kmph), and an exiting velocity range 220comprising a lower bound 223 (at 0 kmph) and an upper bound 226 (at 5kmph). Similarly, the “Car” operation profile has an entering velocityrange 240 comprising a lower bound 243 (10 kmph) and an upper bound 246(150 kmph), and an exiting velocity range 250 comprising a lower bound253 (5 kmph) and an upper bound 256 (150 kmph). A third exemplaryoperation profile, “Airplane”, has an entering velocity range 270comprising a lower bound 273 (250 kmph) and an upper bound 276 (1000kmph), and an exiting velocity range 280 comprising a lower bound 283(200 kmph) and an upper bound 286 (1200 kmph).

Based on the example shown in FIG. 2, when the mobile deviceimplementing the method embodiment described above moves from Okmph to25 kmph, the method switches the mobile device to the “Car” operationprofile, because it is within the 10-150 kmph entering velocity range240 of the “Car” profile. While continuing to monitor its velocity, themobile device remains in the “Car” profile even as the velocity dipsbelow 10 kmph to 7 kmph. The method will only exit the “Car” profilewhen the velocity of the mobile device is below 5 kmph or above 150kmph. Following this case, when the velocity drops to 5 kmph, the methodwill switch from “Car” profile to “Walk” profile, because the enteringvelocity range 210 of “Walk” covers the 0-5 kmph span. In the example ofthe “Walk” profile, the exiting velocity range 220 is also 0-5 kmph, andleaving this range will cause the method to exit the “Walk” operationprofile. The “Airplane” profile operates in a similar way, according tothis embodiment of the present invention, so further description isomitted.

One notes that the above examples show exiting velocity ranges being thesame or “wider” than the entering velocity ranges; this is not alimitation of the present invention, since it is apparent that there isno restriction between the relativity of entering and exiting velocityranges. Additionally, the entering and exiting velocity ranges of the“Walk” operation profile are the same; as is clear from above, this isalso permitted and certainly within the scope of this invention. Notshown in FIG. 2 is a situation where entering and/or exiting velocityranges of different operation profiles are overlapping: in such cases,the method should include the necessary logic and decision-makingprocedures to ensure smooth operation and operation profile switching,but a person of ordinary skill in the art should already understandthis.

In a further enhancement to the above embodiments, the method canfurther comprise storing the current operation profile of the mobiledevice as a “previous operation profile” when switching to a newoperation profile, and then when the velocity of the mobile device iswithin the velocity range of the previous operation profile again,returning to the previous operation profile. FIG. 3 is a state diagramfor this embodiment of the present invention for assisting anexplanation of this scenario. The diagram 300 shows an “Original” (or“Normal”) profile 395, an “Airplane” profile 375, a “Car” profile 345,and another profile 315 (which we may take as similar the “Walk” profilein FIG. 2, for the sake of simplicity). The profile condition 310 andthe restore condition 320 for the profile 315 are substantially similarto the relationship between the entering velocity range 210 and theexiting velocity range 220 for the “Walk” profile (FIG. 2). By the sametoken, one can draw parallels between the “Car” profile 345 and the“Car” profile in FIG. 2, with the profile condition 340 and restorecondition 350 being similar to the entering and exiting velocity ranges240 and 250, respectively. FIG. 3 shows, then, when profile conditionsfor a certain operation profile are satisfied, the mobile device isswitched to that profile; when the restore conditions are met—saidanother way, when the profile conditions for another profile are met—themobile device is returned to the stored “previous operation profile”.Though not explicitly shown in FIG. 3, additional profile switchingpaths are also possible. The present invention includes embodimentswherein the mobile device can switch between different operationprofiles (say, “Car” profile 345 and “Airplane” profile 375) withouthaving to return to the “Original” profile 395, and such implementationswill depend on specific design requirements and configurations.

It should also be noted here that the profile conditions (310, 340, 370)and restore conditions (320, 350, 380) shown in FIG. 3 can encompassother factors and requirements besides the respective entering andexiting velocity ranges previously described: additional methodintelligence or processing can be implemented to provide smoother andmore appropriate profile switching on the mobile device. Switching to atarget operation profile of the mobile device can be according to a timeduration of the mobile device being within a velocity range of thetarget operation profile: for instance, an optional requirement could bethat the mobile device must be traveling at between 10 kmph and 150 kmphfor at least 3 minutes before switching to the “Car” profile. In anotherembodiment, switching to a target operation profile of the mobile deviceis further according to statuses of other devices connected to themobile device, such as the accessories currently in use with the mobiledevice. One example of this embodiment requires the mobile device to betraveling within the “Car” profile velocity range and to be connectedeither to a wired headset, car kit, or a Bluetooth™ enabled wirelessheadset. It becomes apparent that any number of different factors andrequirements can be combined with the velocity monitoring in the mobiledevice to follow in the spirit of the present invention, and should beconsidered within its scope.

FIG. 4 shows a method according to an embodiment of the presentinvention, suggesting an interaction 400 between a mobile device and ageographic information system (GIS) module or device. The GIS module canbe a Global Navigation Satellite System (GNSS) or Global PositioningSystem (GPS) module; in this case, we'll say it is a GPS module. Themobile device may include the GIS module within it, can be a separatedevice that is connected in some manner; for this example, we'll assumethe mobile device has a GIS module inside it (so the velocity of the GISmodule is substantially the same as that of the mobile device). Thesteps shown for the mobile device (left) portion of the interaction are:

-   Step 435: Define a velocity range table.-   Step 440: Register the velocity range table to GPS module.-   Step 455: Listen for notification from GPS module.-   Step 490: Switch between the operation profiles of the mobile device    according to the notifications from the GPS module.

The steps shown for the GPS module (right) portion of the interactionare:

-   Step 450: Monitor the velocity of the mobile device.-   Step 460: When velocity matches any predetermined velocity ranges,    proceed to Step 465; when not, return to Step 450.-   Step 465: Notify mobile device of the change in velocity range.

Please note that the step numbers in FIG. 4 are ordered such that theirchronological order is approximately according to their last two digits(e.g., Step 490 normally follows Step 465); numbers with last two digitscorresponding to those from FIG. 1 are substantially similar (e.g.,Steps 190 and 490).

The interaction flowchart 400 begins with Step 435, which defines avelocity range table in the mobile device. This can be done in a similarmanner to Step 130 in FIG. 1, and could be a process allowing the userto configure the details. Next, Step 440 registers the velocity rangetable to the GPS module (the right side of the figure), and then themobile device portion simply waits and listens for some notificationfrom the GPS module (Step 455). Meanwhile, the GPS module commencesmonitoring the velocity of the mobile device in Step 450. Step 460checks whether the velocity matches any predetermined velocity ranges.When there is a match to a different velocity range (than the current),the method proceeds to Step 465, where the mobile device is notified ofthe change in the velocity range; when not, it returns to Step 450. Whena notification is received from the GPS module in Step 465, the mobiledevice undergoes Step 490 to switch between the operation profiles ofthe mobile device. In a normal scenario, the GPS module would continueto be monitoring the variation in its velocity, and notifies the mobiledevice at each time a change in the velocity range occurs.

Please refer now to FIG. 5 for a method according to another embodimentof the present invention. As before, the step numbers in the flowchartfigures are ordered such that their chronological order is approximatelyaccording to their last two digits; numbers with last two digitscorresponding to those from FIGS. 1, 4 and 5 are substantially similar(e.g., Steps 190 and 490).

-   Step 440: Register the velocity range table to GPS module.-   Step 445: Command GPS module to monitor the velocity of the mobile    device.-   Step 455: Listen for notification from GPS module.-   Step 480: Velocity is in a different velocity range? If yes, proceed    to Step 485; otherwise, return to Step 455.-   Step 485: Additional switching requirements met? If yes, proceed to    Step 490; otherwise, return to Step 455.-   Step 490: Switch to the new operation profile of the mobile device.

Readers will notice that the flowchart of FIG. 5 is similar to that ofFIG. 4, containing numerous overlaps; these overlaps will not bedescribed again in detail. FIG. 5 further assumes the division of tasksbetween the mobile device and its GPS module, however, and digs furtherinto the step details following a notification of a velocity change. InStep 445, after registering the velocity range table to the GPS module,the mobile device commands the GPS module to begin monitoring thevelocity and then waits and listens for a notification (Step 455). Whena notification is received from the GPS module (Step 470 of FIG. 4), acheck is made to see whether the current velocity range is differentfrom the previous one. When this is true, Step 485 is executed;otherwise, no profile changing need take place, and the flowchartreturns to Step 455 to wait for another notification. In Step 485,additional switching requirements (if any) are checked to see if theyare also met: when all requirements are satisfied, the method proceedsto Step 490 (switching to the new operation profile), or else theflowchart goes back to Step 455.

In Step 485, the additional switching requirements can be many,depending on specific configurations or implementation designs. Forinstance, the check could comprise something as simple as notifying theuser when switching between operation profiles of the mobile device, andreceiving user confirmation (to proceed) or receiving a rejection by theuser (in which case, no profile switch is done). As mentioned prior,other additional requirements or factors can be to check the existenceor connection of accessories, or extra logic on the recent behavior ofthe device (e.g., having not changed a profile in at least X minutes, orat most Y minutes). Another embodiment comprises a condition forswitching between the operation profiles of the mobile device furtheraccording to the historical user preferences. Persons of ordinary skillin the art can surely develop other examples after reading thisdisclosure.

Please now refer to FIG. 6, a method for monitoring the velocity of themobile device, according to another embodiment of the present invention.The method shown in FIG. 6 can be roughly seen as equivalent to Step450, 460 and 470 shown in FIG. 4, the step of monitoring the velocity ofthe mobile device, as performed by the GPS module. Here, after beingcommanded by the mobile device to begin monitoring the velocity (Step445 in FIG. 5), the GPS module proceeds to check the current velocity ofthe mobile device against a plurality of velocity ranges existing in thevelocity range table (registered in Step 440 of FIG. 4). FIG. 6 gives anexample of how this check could be implemented: the current velocity issequentially checked against each velocity range in Steps 458A through458X to determine which (if any) of the notification steps 470A through470X should be done. When, in Step 458A (for example), the velocity isfound to match the checked velocity range, then Step 470A is executed tonotify the mobile device of the change in velocity range. When the checkin Step 458A is false, however, the check proceeds to Step 458B to checkthe next velocity range, and so on. Clearly, this is not the only methodby which a check against a series of velocity ranges can be implemented;other methods are also possible, and should be considered in the scopeof this invention.

Delving further into Step 485, and related closely to Step 450 justdiscussed, another consideration is presented in FIG. 7, where themethod adds onto those already disclosed by further ranking a priorityorder of the operation profiles in the mobile device. This additionalmethod determines at least one candidate operation profile for which thevelocity of the mobile device is within the velocity range of thecandidate operation profile, and then switches to the one of thosecandidate profiles with the highest priority. The priority ranking usedhere can be arranged in numerous ways, and the priority diagram 700 ofFIG. 7 shows an example where the priority order is determined in orderof descending velocity range, from highest priority to lowest. In thediagram, the various profiles 710, 730, 750, . . . 770 are eachassociated with a priority ranking 720, 740, 760, . . . 780. In thisparticular example, the “Airplane” profile has a higher priority rankingthan the “Car” profile, which in turn is higher than other profiles.Each of the profiles has also associated with it at least one velocityrange, and other optional conditions (shown, but not marked) forentering and/or exiting the respective profiles; these features havealready been explained in some detail above. Please note that theexample shown in diagram 700 is arbitrary: any other number and/orarrangement of profiles are possible, and depend greatly upon specificimplementations of the present invention.

Now please turn your attention to FIG. 8, which is a block diagram of amobile device according to one embodiment of the present invention. Themobile device 800 of FIG. 8 comprises two larger portions: the mobiledevice “portion” 810, and the GPS portion 860. Please keep in mind thatthe GPS portion 860 needn't be GPS; any functional GIS equivalent, suchas a GNSS system, will suffice for the purposes of the presentinvention. Please note that although some descriptions of this mobiledevice in this example are well suited towards mobile phones, it is anarbitrary selection for illustration purposes only and is not intendedas a limitation to the present invention.

The mobile device portion 810 comprises an operation profile database820, an operation profile switching module 830, and an event listener840. The GPS portion 860 comprises a velocity monitoring module 870, aGPS module 880 (which includes GPS firmware and a GPS receiver), and anevent notifier 890. There is additionally a velocity and profile table850 which may exist in either the mobile device portion 810 or the GPSportion 860, depending upon design and other requirements.

The operation profile database 820 has a plurality of operation profilesas described in the method embodiments above, whereas the velocity andprofile table 850 maps a velocity range (or more, in the case ofentering and exiting velocity ranges) to each operation profile in theoperation profile database 820. The velocity monitoring module 870 isfor monitoring the velocity of the mobile device and GPS module 880,since we are still assuming in this example that the two are portions ofone device (though this may not be the case in other embodiments of thepresent invention). The results of the velocity monitoring module 870are relayed through the event notifier 890 to the event listener 840 inthe mobile device portion 810, which then invokes the operation profileswitching module 830. The operation profile switching module 830 is forswitching between the operation profiles of the mobile device 800according to the velocity of the mobile device 800, and the velocity andprofile table 850. Note that the operation profile switching module 830will, in certain embodiments, perform additional logic based on thevelocity of the mobile device 800 and other additional factors mentionedabove.

Similar options and features as presented in the different embodimentsin the method examples are also valid when considering the mobile deviceembodiment of the present invention. For instance, operation profileswitching module 830 (in one implementation) will first store thecurrent operation profile as a previous operation profile when switchingto a new operation profile, and will return to this previous operationprofile when the mentioned restore conditions are met again. Theoperation profile switching module 830 in another example will alsonotify the user when switching between profiles, which can optionally berejected by the user. As a further option, operation profile switchingmodule 830 can store both an entering velocity range and an exitingvelocity range for each operation profile in the velocity and profiletable 850; the operation profile switching module 830 then switches to atarget profile when the velocity of the mobile device is within theentering velocity range of that target profile and is also outside ofthe exiting velocity range of the current operation profile. As before,the entering velocity range and the exiting velocity range in this casecan be different from one another.

Previous given examples are also valid as embodiments with additionalprofile switching criteria for the operation profile switching module830: priority ranking, historical user preferences, minimum or maximumtime durations in a particular profile, and the like. Since theimplementation for adding such logic is commonly known to those skilledin the art, further description is omitted.

Please note that although the current examples are shown utilizing aGlobal Navigation Satellite System (GNSS) or Global Positioning System(GPS) device, this is only intended for clarity of explanation and isnot meant as a limitation to the present invention. It should also benoted that although the examples given in this disclosure lendthemselves easily to the conception of a mobile phone enabled with GPStechnology, the application to a mobile phone is not meant to be alimitation of the scope of this invention. The present invention can beapplied to any mobile or portable device which is enabled with any typeof GIS module inside, even ones where the geographic information isproduced by indirectly measuring velocity (such as by triangulation fromother data sources). Such applications and embodiments also obey thespirit of, and should be considered within, the scope of the presentinvention.

To drive this point home, although the present invention and itsadvantages have been described in detail, it should be understood thatvarious changes, substitutions and alterations can be made hereinwithout departing from the spirit and scope of the invention as definedby the appended claims. For example, many of the processes discussedabove can be implemented in different methodologies and replaced byother processes, or a combination thereof.

Moreover, the scope of the present application is not intended to belimited to the particular embodiments of the process, machine,manufacture, composition of matter, means, methods and steps describedin the specification. As one of ordinary skill in the art will readilyappreciate from the disclosure of the present invention, processes,machines, manufacture, compositions of matter, means, methods, or steps,presently existing or later to be developed, that perform substantiallythe same function or achieve substantially the same result as thecorresponding embodiments described herein may be utilized according tothe present invention. Accordingly, the appended claims are intended toinclude within their scope such processes, machines, manufacture,compositions of matter, means, methods, or steps.

Those skilled in the art will readily observe that numerousmodifications and alterations of the device and method may be made whileretaining the teachings of the invention.

1. A method for automatically switching operation profiles on a mobiledevice storing an operation profile database having a plurality ofoperation profiles, the method comprising: mapping a velocity range toeach operation profile to thereby form a velocity and profile table;monitoring a velocity of the mobile device; and switching between theoperation profiles of the mobile device according to the velocity of themobile device, and the velocity and profile table.
 2. The method ofclaim 1, further comprising notifying a user when switching betweenoperation profiles of the mobile device.
 3. The method of claim 1,further comprising: switching between the operation profiles of themobile device further according to a user confirmation, whereinswitching between the operation profiles of the mobile device can berejected by the user.
 4. The method of claim 1, further comprising:switching between the operation profiles of the mobile device furtheraccording to the historical user preferences.
 5. The method of claim 1,further comprising: switching to a target operation profile when thevelocity of the mobile device is within the velocity range of the targetoperation profile.
 6. The method of claim 1, further comprising: mappingan entering velocity range and an exiting velocity range to eachoperation profile in the velocity and profile table; and switching to atarget operation profile when the velocity of the mobile device iswithin the entering velocity range of the target operation profile andis outside of the exiting velocity range of a current operation profile,wherein the entering velocity range is different from the exitingvelocity range.
 7. The method of claim 1, further comprising: ranking apriority order of the operation profiles; determining at least onecandidate operation profile for which the velocity of the mobile deviceis within the velocity range of the candidate operation profile; andswitching to a target operation profile being a candidate operationprofile having a highest priority.
 8. The method of claim 7, wherein thepriority order is determined in order of descending velocity range. 9.The method of claim 1, further comprising: switching to a targetoperation profile of the mobile device further according to a timeduration of the mobile device being within a velocity range of thetarget operation profile.
 10. The method of claim 1, further comprising:switching to a target operation profile of the mobile device furtheraccording to statuses of other devices connected to the mobile device.11. The method of claim 1, further comprising: monitoring the velocityof the mobile device utilizing a Global Navigation Satellite System(GNSS) device.
 12. A mobile device for automatically switching operationprofiles, comprising: an operation profile database having a pluralityof operation profiles; a velocity and profile table formed by mapping avelocity range to each operation profile; a velocity monitoring modulefor monitoring a velocity of the mobile device; and an operation profileswitching module for switching between the operation profiles of themobile device according to the velocity of the mobile device, and thevelocity and profile table.
 13. The mobile device of claim 12, whereinthe operation profile switching module is further for notifying a userwhen switching between operation profiles of the mobile device.
 14. Themobile device of claim 12, wherein the operation profile switchingmodule is further for switching between the operation profiles of themobile device further according to a user confirmation, and switchingbetween the operation profiles of the mobile device can be rejected bythe user.
 15. The mobile device of claim 12, wherein the operationprofile switching module is further for switching between the operationprofiles of the mobile device further according to the historical userpreferences.
 16. The mobile device of claim 12, wherein the operationprofile switching module is further for switching to a target operationprofile when the velocity of the mobile device is within the velocityrange of the target operation profile.
 17. The mobile device of claim12, wherein the velocity and profile table is further for mapping anentering velocity range and an exiting velocity range to each operationprofile in the velocity and profile table; and the operation profileswitching module is further for switching to a target operation profilewhen the velocity of the mobile device is within the entering velocityrange of the target operation profile and is outside of the exitingvelocity range of a current operation profile, and the entering velocityrange is different from the exiting velocity range.
 18. The mobiledevice of claim 12, wherein the operation profile switching module isfurther for ranking a priority order of the operation profiles,determining at least one candidate operation profile for which thevelocity of the mobile device is within the velocity range of thecandidate operation profile, and switching to a target operation profilebeing a candidate operation profile having a highest priority.
 19. Themobile device of claim 18, wherein the priority order is determined inorder of descending velocity range.
 20. The mobile device of claim 12,wherein the operation profile switching module is further for switchingto a target operation profile of the mobile device further according toa time duration of the mobile device being within a velocity range ofthe target operation profile.
 21. The mobile device of claim 12, whereinthe operation profile switching module is further for switching to atarget operation profile of the mobile device further according tostatuses of other devices connected to the mobile device.
 22. The mobiledevice of claim 12, wherein the velocity monitoring module utilizes aGlobal Navigation Satellite System (GNSS) device.